Method and system for managing destination addresses

ABSTRACT

A method for downloading destination addresses associated with a given client device from a server to the client device is disclosed. The method comprises the steps of determining a resource limitation of the client device, sorting the addresses, and transmitting a subset of the sorted addresses from the server to the device, wherein the transmitted sorted address subset is determined by the resource limitation. There is also provided a system and server for supporting Instant Messaging (IM). The system comprises a telecommunications network interconnecting a plurality of IM clients and an IM server, the plurality of IM clients configured to exchange instant messages with one another via the telecommunications network and the IM server, each of the IM clients having an associated IM address, the IM server comprising a memory for storing a plurality of IM addresses, a set of the IM addresses corresponding to each of the IM clients and wherein a given set comprises at least one IM address other than an IM address of the IM client to which the given set corresponds, wherein on occurrence of a triggering event associated with a particular IM client the IM server selects a subset of the IM addresses from the set of addresses corresponding to the particular IM client based on a resource limitation of the particular IM client and transmits the selected IM address subset to the particular IM client.

The present application claims priority from U.S. Patent Application No. 60/653,127 filed on Feb. 16, 2005, the entire contents of which is incorporated herein by reference.

FIELD OF THE INVENTION

The present invention relates to a method and system for managing destination addresses. In particular, the present invention relates to a method for and system for managing and downloading destination addresses to a mobile device having limited resources, for example in terms of memory and/or bandwidth, based on one or more variable attributes of the destination address.

BACKGROUND OF THE INVENTION

As known in the art, Instant Messaging (IM) services such as AIM and ICQ, amongst others, allow a user to maintain a contact list (or buddy list) comprising the destination addresses of other users they may wish to interact with. A user is alerted when another user matching one of the entries in his contact list goes online, and a real-time exchange of messages can take place with any of these users provided they are currently online (present) and not otherwise busy. In one embodiment of an IM service, initiating sending a message to a user opens up a small window, or dialog box, through which both users can interact in real-time by typing in text.

IM services, as are the majority of open distributed applications, are often based on a client-server architecture, where a large number of clients, typically in the form of software modules located on devices being used by individual users (such as a personal computer, PDA or the like) communicate with one or more centralised servers. The server typically responds only to requests for services which are initiated by the client. In this regard, the client will initiate establishment of a (logical) communications channel with the server by “logging on”, and once established bidirectional communications can take place between client and server. In particular, once a communications channel has been established between the server and a client, the channel can be taken advantage of for the transfer of relevant IM service information. As stated above, one type of information provided and managed by IM services is contact lists.

For IM services which are implemented using personal computers and high speed wired or wireless networks, arbitrarily long contact lists may be used without any significant impact on system performance. Additionally, the attributes (or status) of individual entries in the contact list typically change over time as users come online or go offline, become engaged with other users, etc. In order to support the display of arbitrarily long contact lists and maintain currency of the displayed information, sizeable display capabilities, large available memory and frequent signaling are required. In wireless networks, where the constraints on device capabilities and network capacity are more severe, storing and maintaining status information for arbitrarily large lists of destination addresses is much more challenging.

IM services typically additionally allow a user to group contacts into smaller subsets of lists (co-workers, buddies, etc.) for easier manipulation. Existing wireless mobile instant messaging systems allow the user to create a specific contact list for usage on a mobile device. For example, U.S. Pat. No. 6,714,793 for a “method and system for instant messaging across wireless networks and a public data network”, the entire contents of which is incorporated herein by reference, describes a communications system for sending a message from a wireless device over a wireless communication network. The disclosed method allows for use of destination addresses that were previously stored on the device. The method also allows the user to add new destination addresses via the device handset, but does not allow additional addresses to be collected from the communications network.

Similarly, the Open Mobile Alliance (OMA) Wireless Village Standard allows for the mobile device to request the network to supply a contact list of destinations addresses using the ListManageRequest primitive. However, no mechanism is provided for limiting the size of a contact list, for example by requesting less than the complete contact list. Furthermore, there is no mechanism for allowing the server to interactively modify the content of a contact list located at a client device during a session. The Wireless Village Standard allows for the user to modify the contact list content using the ListManageRequest, but this again does not allow for dynamic management on the part of the server to modify the content of the contact list.

Mobile devices usually contain an address book (AB), where the user may enter phone numbers of contacts. This address book may also include additional fields such as email addresses. However, these address books do not include fields for destination addresses for instant messaging contacts. As a result, there is no mechanism for associating instant messaging destination addresses with other identities in the mobile device (e.g. with the information in the device address book).

SUMMARY OF THE INVENTION

As stated above, systems providing IM services provide for a list of destination addresses (contact lists or buddy lists). These lists furthermore show the presence status (or attributes) of the user identified by the destination addresses.

A mechanism for truncating the list size is required, as well as a mechanism for updating the list on the mobile client device. In particular, in wireless networks, the problem of updating such lists is further compounded by the fact that users typically require access to their IM service for extended periods of time, during which the presence status of the destination addresses may change repeatedly. In one embodiment, the proposed mechanism provides for more efficient use of network resources by updating contact lists only when the underlying IM service is actively in use on the client device and when the changes are sufficient to impact usability. The proposed mechanism also takes into consideration that there are variations in capabilities of client devices and transport mechanisms.

In order to overcome the above and other drawbacks, a first part of the present invention relates to the management of a set of destination addresses and the status of the users identified by these destination addresses for instant messaging clients, in particular on mobile devices.

There is provided a method for downloading destination addresses associated with a given client device from a server to the client device. The method comprises the steps of determining a resource limitation of the client device, sorting the addresses, and transmitting a subset of the sorted addresses from the server to the device, wherein the transmitted sorted address subset is determined by the resource limitation.

There is also provided a system for providing Instant Messaging (IM). The system comprises a telecommunications network interconnecting a plurality of IM clients and an IM server, the plurality of IM clients configured to exchange instant messages with one another via the telecommunications network and the IM server, each of the IM clients having an associated IM address, the IM server comprising a memory for storing a plurality of IM addresses, a set of the IM addresses corresponding to each of the IM clients and wherein a given set comprises at least one IM address other than an IM address of the IM client to which the given set corresponds, wherein on occurrence of a triggering event associated with a particular IM client the IM server selects a subset of the IM addresses from the set of addresses corresponding to the particular IM client based on a resource limitation of the particular IM client and transmits the selected IM address subset to the particular IM client.

Additionally, there is provided a server in a system comprising a telecommunications network interconnecting a plurality of Instant Messaging (IM) clients with the server, each of the IM clients having an associated IM address. The server comprises a memory for storing a plurality of IM addresses, a set of IM addresses corresponding to each of the IM clients and wherein a given set of IM addresses comprises at least one IM address other than an IM address of the IM client to which the given set corresponds, wherein on occurrence of an event associated with a particular IM client the server selects a subset of IM addresses from the set of addresses corresponding to the particular IM client based on a resource limitation of the particular IM client and transmits the selected IM address subset to the particular IM client.

Additionally, the present invention relates to the management of users identified by multiple destinations addresses.

In systems providing IM services, users are frequently identified by specific destination addresses or identifiers within the system. These users may also be known through other identities in the mobile devices, such as their name, nick name, telephone number or e-mail address. There is currently no mechanism available by which the identity of a user in a system providing IM services can be associated with other identities that the same user has elsewhere in a mobile device for retrieval/storage of the IM destination address from/to another identity associated with the user, or another identity from/to the IM destination address.

In order to overcome the above and other drawbacks, a second part of the present invention provides for a method for handling user identifiers in a client device associated with a user and configured for providing communication between the user and a plurality of other users via an IM service and at least one additional communication service, the IM service comprising an IM server, each of the users identified by a unique IM identifier and at least one additional identifier uniquely identifying each of the users when using the at least one additional communication service. The method comprising the steps of providing a memory, storing a plurality of additional identifiers in the memory, receiving a contact list from the IM server, the list comprised of at least one entry comprising an IM identifier and at least one additional identifier, and for each entry in the contact list, comparing the received at least one additional identifier with the stored additional identifiers, selecting one of the stored additional identifiers which matches the received at least one additional identifier and associating the IM identifier with the selected stored additional identifier.

Additionally, there is provided a method for communicating between a user and another user, the user connected with the other user via a plurality of telecommunication services including an IM service. The method comprises the steps of receiving an IM message from the other user via the IM service, prompting the user to select one telecommunication service from the plurality of telecommunication services for responding to the received IM message, and transmitting a response to the other user using the selected telecommunication service.

Additionally, although the description of the systems, devices and methods hereinbelow is within the context of a mobile IM service, they also apply more generally to services where:

-   -   ? The user is presented with a set of destination addresses. Due         to the constraints of the terminal device, this set of addresses         may require significant compression if it is to be displayed or         stored on a mobile device, as compared to when displayed on a PC         device;     -   ? the destination addresses possess dynamic attributes that are         relevant as discrimination criteria for compressing the set, and         are susceptible to change while the user is accessing and using         the service; or     -   ? the user accesses and makes use of the service for periods of         sufficient duration for significant changes to occur in the         status of the dynamic attributes of the destination addresses.

Especially when one or more of these conditions is present, the systems, devices and methods described in hereinbelow by way of an illustrative embodiment thereof enable a compressed set of destination addresses to be initially provided to the mobile device based on relevant dynamic (variable) attributes of the destination addresses, and to be subsequently updated based on the changes in the status the dynamic (variable) attributes. As a first example, these methods could be applied to a Push-To-Talk (PTT) service, in which the compression of the set of destination addresses provided to the mobile device would be based on the availability of the destination addresses for engaging in a PTT call, and not already engaged in another call. As a second example, these methods could be applied to a gaming service, in which the compression of the set of destination addresses provided to the mobile device would be based on the availability of the destination addresses for engaging in the game, and not already playing another game.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is schematic diagram of an instant messaging system in accordance with an illustrative embodiment of the present invention;

FIG. 2 is a front view of a mobile client device in accordance with an illustrative embodiment of the present invention; and

FIG. 3 is a flowchart of a method for managing a set of destination addresses stored on a mobile device.

DETAILED DESCRIPTION OF THE ILLUSTRATIVE EMBODIMENTS

Referring now to FIG. 1, a system for managing contact addresses, generally referred to using the reference numeral 10, and in accordance with an illustrative embodiment of the present invention will be described. The system 10 comprises a plurality of clients as in 12 which are arranged for communication with one or more IM servers as in 14 in a client-server relationship. In this regard, communication pathways between individual clients, for example between client 12 ₁ and client 12 ₂, are established via the server(s) 14. Communication bearer links, or transport, between clients and server can be supported by a variety of communications means, for example wireless connections 16 or wired connections 18, and typically consist of a concatenation of heterogeneous communication systems, such as mobile operator networks 20, broadband networks 22 such as the Internet and local area networks (LANs) 24, etc . . . . As a result, the clients as in 12 may be either mobile, for example in the form of a software module executing in a mobile client device (such as a mobile handset or the like), or fixed, for example in the form of a software module executing in a fixed client device (such as a desk top system or the like).

Referring to FIG. 2 in addition to FIG. 1, each client as in 12 is further combined in the client device with a user interface comprised of a display 26 and an input device 28, such as a keyboard, touch screen, mouse, etc. Additional items, typically in the form of a software application, such as a client device address book 30 are also provided in particular embodiments.

Referring now to FIG. 3 in addition to FIGS. 1 and 2, an illustrative embodiment of a mechanism for managing the set of destination addresses stored on a mobile device will now be described with reference to the flowchart.

When presented with a contact list comprised of a set of destination addresses to be downloaded to a client 12, the server 14 determines the size suitable for the client 12 and the transport being used (‘*1’ in the flowchart). The client capabilities, or resource limitations, may be previously known to the server 14.(for example, based on a number of preset configurations stored in memory), or may be supplied by the client 12 at the time that the request to download the contact list of destination addresses is made. Alternatively, the server 14 may determine, for example based on the type of transport (for example, SMS), that the list must be fixed at a certain predetermined limit (for example, thirty (30) destination addresses).

If the number of destination addresses in a contact list is greater than allowed for a particular client 12 or transport, the system selects which subset will be sent to the client 12 (‘*2’ in the flowchart). For example, referring now to FIG. 2, to provide a visual indication to the user, each destination address as in 32 is typically tagged with a descriptive icon as in 34 indicating the current presence status (or variable attribute) of the user identified by that particular destination address 32. Typically, presence status indicates one of “online”, “busy”, “away”, or “offline”. In an illustrative embodiment, the destination addresses 32 in the contact list would be prioritized according to their presence status and those addresses whose presence status indicates that they are “online” would be downloaded first, followed by destination addresses whose presence status indicates that they are “busy”, “away”, etc., until the maximum number of destination addresses is reached.

Referring back to FIG. 1 and 3 in addition to FIG. 2, as the presence status of the destination addresses change over time (e.g. from “offline” to “online”), a mechanism is provided for refreshing the set of destination addresses 32 in the client 12. A number of different triggers may be used (‘*3’ in the flowchart). For example, one trigger may be that the user manually refreshes the set by selecting via the input device 28 a menu entry which is displayed to the user in the display 26, triggering an action in the client 12. Alternatively, the server 14 could detect that it is an appropriate time to send an updated set of destination addresses 32 to the client 12 such as the expiry of a predetermined time delay or a change in state of one of the destination addresses as in 24. For example, using the Wireless Village protocol as a basis (with the addition of an extension to the “ListManage” primitive to indicate a dynamic update of the destination addresses), a manual refresh may be generated using the “ListManage” primitive. Alternatively, another method would allow the server 14 to include the set of destination addresses 32 (or update to the set) during a presence update. This could be accomplished with the addition of an appropriate extension to the Wireless Village primitives GetPresence or PresenceNotification.

Once the server 14 has detected a trigger to dynamically update the set of destination addresses 32, the server 14 must again select which subset will be sent to the client 12 (‘*4’ in the flowchart). As the client 12 is currently in a session, there may be one or more destination addresses having a presence status indicating “in conversation”. In this example, an illustrative embodiment of selecting the subset of destination addresses 32 would be to prioritize them in the order “in conversation”, “online”, “busy”, “away”, or “offline” and download those destination addresses 32 having presence status indicating “in conversation” first, followed by “online”, “busy”, “away”, and “offline” up until the maximum number of destination addresses has been downloaded.

In an alternative embodiment, the entire contact list could be divided into a series of smaller contact lists, each of the smaller contact lists comprising a subset of all those destination addresses which would otherwise form part of the contact list. Provision would also be made to allow the user to view the smaller contact lists one list at a time. For example, the default contact list may include all destinations addresses where the presence status indicates “online”, with subsequent contact lists containing the remaining destination addresses arranged, for example, alphabetically. Illustratively, the client 12 would retrieve the identities of the set of smaller contact lists with the Wireless Village primitive GetListRequest. The default list could then be retrieved using the ListManageRequest primitive. The user would then be presented with the option to view the other lists (e.g. using a “next page” command or the like). When selected, the client would use the ListManageRequest primitive with reference to the subsequent contact list identifier (Contact-List-ID) to download the next in the series of smaller contact lists.

Referring now back to FIGS. 1 and 2, on login to an IM service for example, the server 14 provides to the client 12, typically in the form of a contact list (not shown) associated with the user of the client 12, one or more attributes associated with those destination addresses as in 32 in the contact list. These attributes can include, for example, a plurality of identifiers such as the destination address in the IM service (User ID), contact name, nick name as well as identifiers identifying a given user on other communication systems, as email address(es), telephone number(s), etc. In an alternative embodiment of the present invention the client 12 inspects the device address book 30 together with the contact list to determine if some of these identifiers match with equivalent identifiers of entries stored in the device address book 30. Upon positive match, the client 12 associates the destination address 32 with the corresponding entry stored within the device address book 30. This association can be automatic, or alternatively could require confirmation from the user.

The IM service may also offer the user the ability to manually associate a destination address 32 with an entry stored within the device address book 30 (for example, the client 12 could prompt the user the option of selecting an entry in the device address book 30 and linking the destination address 32 to the entry). Once this association is made, the user is provided with the option of communicating with a particular destination address via a means other than the IM service. For example, the user may select to transmit an e-mail message or to phone the other user identified by that destination address.

Alternatively, the association could be stored by the client 12 within the device address book 30 following which the device address book 30 could be used by the to user to send instant messages to the user identified by the entry in the device address book 30.

Although the present invention has been described hereinabove by way of an illustrative embodiment thereof, this embodiment can be modified at will without departing from the spirit and nature of the subject invention. 

1. A method for downloading destination addresses associated with a given client device from a server to the client device, the method comprising the steps of: determining a resource limitation of the client device; sorting the addresses; and transmitting a subset of said sorted addresses from the server to the device; wherein said transmitted sorted address subset is determined by said resource limitation.
 2. The method of claim 1, wherein each of the addresses has at least one variable attribute and wherein said sorting step comprises sorting said addresses on their at least one variable attribute.
 3. The method of claim 1, wherein each of the addresses has at least one variable attribute and wherein said sorting step comprises prioritizing the addresses according to their attributes, wherein said subset transmitting step comprises transmitting said subset of prioritized addresses from the server to the device in order of their priority, and further wherein the number of addresses in said transmitted subset is determined by said resource limitation.
 4. The method of claim 1, wherein each of the addresses has at least one variable attribute and wherein each of the destination addresses corresponds to a user, wherein the at least one variable attribute is a presence attribute indicating a current status of the user corresponding to the address as being one of a plurality of different presence states including at least an online state and further wherein said address subset comprises addresses wherein said presence attribute indicates the user as being online.
 5. The method of claim 1, wherein each of the addresses has at least one variable attribute and wherein each of the destination addresses corresponds to a user, wherein the at least one variable attribute is a presence attribute indicating the current status of a user corresponding to the address as being one of a plurality of different presence states selected from the group consisting of online, busy, away and offline and further wherein said address prioritizing step comprises prioritizing addresses having an online presence attribute as highest, addresses having a busy presence attribute second highest, addresses having an away presence attribute third highest and addresses having an offline presence attribute as lowest.
 6. The method of claim 1, wherein the client device and the server are interconnected via at least one wireless communications transport and said resource limitation is a speed of said transport.
 7. The method of claim 1, wherein the client device comprises a memory allocated for storing a received message, and said resource limitation is a number of messages which can be stored in said allocated memory.
 8. The method of claim 1, wherein the client device comprises a memory allocated for storing said transmitted address subset, and said resource limitation is a number of addresses which can be stored in said allocated memory.
 9. The method of claim 1, wherein each of the addresses has at least one variable attribute and further comprising the step of updating said transmitted address subset when at least one of the variable attributes of at least one of the destination addresses changes.
 10. The method of claim 1, further comprising the step of periodically updating said transmitted address subset.
 11. The method of claim 9, wherein each of the addresses has at least one variable attribute and wherein said updating step comprises sorting the addresses according to-their attributes and transmitting a subset of said sorted addresses from the server to the device, wherein said transmitted sorted address subset is determined by said resource limitation.
 12. The method of claim 1, wherein each of the addresses has at least one variable attribute and wherein each address of said transmitted subset have the same at least one variable attribute.
 13. The method of claim 1, wherein each of the addresses has at least one variable attribute and wherein said determined resource limitation is that each address of said transmitted subset shall have the same at least one variable attribute.
 14. The method of claim 1, further comprising, prior to said resource limitation determining step, a step of providing a plurality of predefined client device types, each of said predefined types comprising at least one predetermined resource limitation, and further wherein said resource limitation determining step comprises identifying a type of the client device and correlating said identified type with one of said predefined types.
 15. The method of claim 1, further comprising, prior to said resource limitation determining step, a step of logging the client into the server and wherein said at least one predetermined resource limitation is provided by the client to the server during said login step.
 16. The method of claim 15, further comprising, prior to said login step, a step of providing a plurality of predefined client device types, each of said predefined types comprising at least one predetermined resource limitation, wherein said login step comprises the client providing a client device type to the server and further wherein said resource limitation determining step comprises correlating said provided client device type with one of said predefined types.
 17. A system for providing Instant Messaging (IM), the system comprising: a telecommunications network interconnecting a plurality of IM clients and an IM server, said plurality of IM clients configured to exchange instant messages with one another via said telecommunications network and said IM server; each of said IM clients having an associated IM address; said IM server comprising a memory for storing a plurality of IM addresses, a set of said IM addresses corresponding to each of said IM clients and wherein a given set comprises at least one IM address other than an IM address of the IM client to which said given set corresponds; wherein on occurrence of a triggering event associated with a particular IM client said IM server selects a subset of said IM addresses from said set of addresses corresponding to said particular IM client based on a resource limitation of said particular IM client and transmits said selected IM address subset to said particular IM client.
 18. The system of claim 17, wherein each of said IM clients further comprises a variable status and wherein said triggering event occurrence comprises a change in the variable status of an IM client having an address in said set of said IM addresses corresponding to said particular IM client.
 19. The system of claim 18, wherein said selected IM address subset is transmitted to said particular IM client in a Presence Notification primitive.
 20. The system of claim 18, wherein said selected IM address subset includes only IM addresses in said set of said IM addresses corresponding to said particular IM client whose variable status has changed.
 21. The system of claim 17, wherein said triggering event occurrence comprises an expiry of a predetermined amount of time.
 22. The system of claim 17, wherein each of said IM addresses further comprises a variable attribute and further wherein said IM server selects said subset according to said variable attribute.
 23. The system of claim 22, wherein said variable attribute indicates a status of said IM client corresponding to said IM address.
 24. The system of claim 23, wherein said IM client status is selected from a group consisting of online, mobile, busy, away and offline.
 25. The system of claim 17, wherein said particular IM client device comprises a memory allocated for storing said selected IM address subset, and said resource limitation is a number of addresses which can be stored in said allocated memory.
 26. The system of claim 17, wherein said telecommunications network comprises at least one wireless communications transport interconnecting said particular IM client and said IM server and wherein said resource limitation is a speed of said transport.
 27. The system of claim 17, wherein said telecommunications network comprises a wireless transport.
 28. The system of claim 18, wherein said wireless transport is provided via a mobile telephone network.
 29. The system of claim 28, wherein said mobile telephone network is selected from a group consisting of first generation wireless networks, second generation wireless networks and third generation wireless networks.
 30. The system of claim 28, wherein said mobile telephone network is selected from a group consisting of a GSM network, a CDMA network and a TDMA network.
 31. The system of claim 17, wherein said telecommunications network comprises the internet.
 32. The system of claim 17, wherein each of said IM clients is one of a plurality of predefined IM client device types, each of said predefined types comprising at least one predetermined resource limitation and further wherein prior to selecting said IM addresses subset, said IM server identifies a type of said particular IM client device and correlates said identified device type with one of said predefined device types.
 33. The system of claim 17, wherein said particular IM client device comprises a screen for displaying at least a portion of said selected IM address subset, wherein a user of said particular IM client device can command said screen to be refreshed and further wherein said triggering event occurrence comprises the user commanding said screen to be refreshed.
 34. The system of claim 17, wherein said particular IM client device comprises a memory for storing said selected IM address subset and a keyboard for entering additional IM addresses into said particular IM client device memory and wherein said triggering event occurrence comprises a user of said particular IM client entering at least one additional IM address into said particular IM client device memory.
 35. A server in a system comprising a telecommunications network interconnecting a plurality of Instant Messaging (IM) clients with the server, each of the IM clients having an associated IM address, the server comprising: a memory for storing a plurality of IM addresses, a set of IM addresses corresponding to each of the IM clients and wherein a given set of IM addresses comprises at least one IM address other than an IM address of the IM client to which said given set corresponds; wherein on occurrence of an event associated with a particular IM client the server selects a subset of IM addresses from said set of addresses corresponding to said particular IM client based on a resource limitation of said particular IM client and transmits said selected IM address subset to said particular IM client.
 36. A method for handling user identifiers in a client device associated with a user and configured for providing communication between the user and a plurality of other users via an IM service and at least one additional communication service, the IM service comprising an IM server, each of the users identified by an IM identifier and at least one additional identifier identifying each of the users when using one of the at least one additional communication service, the method comprising the steps of: providing a memory; storing a plurality of additional identifiers in said memory; receiving a contact list from the IM server, said list comprised of at least one entry comprising an IM identifier and at least one additional identifier; and for each entry in said contact list, comparing said received at least one additional identifier with said stored additional identifiers, selecting one of said stored additional identifiers which matches said received at least one additional identifier and associating said IM identifier with said selected stored additional identifier.
 37. The method of claim 36, wherein the at least one additional communication service comprises a mobile telephone network and the at least one additional identifier comprises a telephone number.
 38. The method of claim 36, wherein the at least one additional communication service comprises an e-mail service and the at least one additional identifier comprises an e-mail address.
 39. The method of claim 36, further comprising, prior to said associating step, the step of prompting the user to confirm said subsequent associating step.
 40. The method of claim 36, wherein said memory is a digital address book comprising at least one address entry including an IM identifier field and at least one additional identifier field, said storing step comprises selecting an address entry and entering said at least one additional identifier into said selected address entry at least one additional identifier field, said selecting step comprises selecting an address entry corresponding to said matched stored additional identifier and said associating step comprises entering said IM identifier in said selected address entry IM identifier field.
 41. The method of claim 36, wherein the client device comprises a keypad and said storing step comprises entering said at least one additional identifier into said memory using the keypad.
 42. A method for communicating between a user and another user, the user connected with the other user via a plurality of telecommunication services including an IM service, the method comprising the steps of: receiving an IM message from the other user via the IM service; prompting the user to select one telecommunication service from the plurality of telecommunication services for responding to said received IM message; and transmitting a response to the other user using said selected telecommunication service.
 43. The method of claim 42, further comprising, prior to said prompting step, the step of checking if the other user is available via each of the telecommunication services and further wherein said prompting step comprises providing to the user for selection only the available telecommunication services. 